Automated test generation for multi-interface enterprise virtualization management environment

ABSTRACT

Embodiments for automated testing of a virtualization management system are described. According to one aspect, a method includes generating a test case including a plurality of instances of commands and sending the test case to a plurality of interfaces supported by the virtualization management system. The method also includes generating a response file corresponding to each command in the test case. The method also includes comparing results from each interface to an instance of a command and in response to the results from each interface being identical, storing, the results in the response file corresponding to the command. The method also includes reporting an error in response to the results from each interface of the virtualization management system not being identical. The present document further describes examples of other aspects such as systems, computer products.

DOMESTIC PRIORITY

This application is a continuation of U.S. Non-Provisional applicationSer. No. 14/927,583, entitled “AUTOMATED TEST GENERATION FORMULTI-INTERFACE ENTERPRISE VIRTUALIZATION MANAGEMENT ENVIRONMENT”, filedOct. 30, 2015, which is incorporated herein by reference in itsentirety.

BACKGROUND

The present application relates to automated test-case generation, andmore specifically, to automated test-case generation for avirtualization management environment.

Testing often consumes a considerable amount of time when developingsoftware. Typically, a programming background is required to createautomated tests for software applications, application programminginterfaces, software development kits, web services and websites. Mosttest applications require users to learn a specific language to writetests. In addition, when a new instance (build, version, etc.) of aproduct is developed, new or modified tests may be required to ensurethat the new instance of the product performs correctly. Further, thecomplexity and amount of work associated with system level testing ofmulti-interface components in a cloud-based computing infrastructurerenders manual testing to become inefficient and costly as the systemcomponents and complexity increases.

SUMMARY

According to an embodiment, a method for automated testing of avirtualization management system includes generating, by a test server,a test case including a plurality of instances of commands executable bythe virtualization management system. The method also includes sending,by the test server, the test case to each interface of a plurality ofinterfaces supported by the virtualization management system. The methodalso includes generating, by the test server, a response filecorresponding to each unique command in the test case. The method alsoincludes comparing, by the test server, results from each interface toan instance of a command from the test case upon execution of theinstance the command by the virtualization management system. The methodalso includes in response to the results from each interface of thevirtualization management system being identical, storing, by the testserver, in the response file corresponding to the command, the resultsfrom the virtualization management system. The method also includesreporting, by the test server, an error in response to the results fromeach interface of the virtualization management system not beingidentical.

According to another embodiment, a system for automated testing of avirtualization management system includes a memory and a processor. Theprocessor determines a number of interfaces supported by thevirtualization management system; generate a test case includinginstances of commands executable by the virtualization managementsystem. The processor sends the test case for execution by thevirtualization management system via each of the interfaces of thevirtualization management system. The processor generates a responsefile for each unique command in the test case, where the response fileincludes an entry corresponding to result of executing each instance ofthe unique command via each interface of the virtualization managementsystem. The processor compares results of execution, by thevirtualization management system via each interface, of a first instanceof a command in the test case. In response to the results of the firstinstance of the command via each interface being identical, theprocessor appends the results to each response file in the response filecorresponding to the command. In response to the results of the firstinstance of the command via each interface not being identical, theprocessor reports an error.

According to yet another embodiment, a computer product for automatedtesting of a virtualization management system includes computer readablestorage medium. The computer readable storage medium includes computerexecutable instructions to determine a number of interfaces supported bythe virtualization management system. The computer readable storagemedium further includes computer executable instructions to generate atest case including instances of commands executable by thevirtualization management system. The computer readable storage mediumfurther includes computer executable instructions to send the test casefor execution by the virtualization management system via each of theinterfaces of the virtualization management system. The computerreadable storage medium further includes computer executableinstructions to generate a response file for each unique command in thetest case, where the response file includes an entry corresponding toresult of executing each instance of the unique command via eachinterface of the virtualization management system. The computer readablestorage medium further includes computer executable instructions tocompare results of execution, by the virtualization management systemvia each interface, of a first instance of a command in the test case.The computer readable storage medium further includes computerexecutable instructions to, in response to the results of the firstinstance of the command via each interface being identical, append theresults to each response file in the response file corresponding to thecommand. The computer readable storage medium further includes computerexecutable instructions to, in response to the results of the firstinstance of the command via each interface not being identical, reportan error.

BRIEF DESCRIPTION OF THE DRAWINGS

The examples described throughout the present document may be betterunderstood with reference to the following drawings and description. Thecomponents in the figures are not necessarily to scale. Moreover, in thefigures, like-referenced numerals designate corresponding partsthroughout the different views.

FIG. 1 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 2 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 3 illustrates an example virtualization management system inaccordance with an embodiment.

FIG. 4 illustrates an example test server in accordance with anembodiment.

FIG. 5 illustrates a flowchart of example logic to automatically test avirtualization management system in accordance with an embodiment.

FIG. 6 illustrates a flowchart of example logic to automatically test avirtualization management system in accordance with an embodiment.

FIG. 7 illustrates a flowchart of example logic to automatically test avirtualization management system in accordance with an embodiment.

DETAILED DESCRIPTION

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 1 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 2, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 1) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 2 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provides pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and processing and analysis of customerfeedback of applications 96.

Disclosed here are technical solutions for automated testing of amulti-interface virtualization management system, such as for anenterprise. The virtualization management system facilitates theenterprise, such as an organization, to deploy cloud-based computingmanagement based dynamic infrastructure. The complexity and amount ofwork associated with system level testing of a multi-interfacevirtualization management system in a cloud-based computinginfrastructure renders manual testing to become inefficient and costlyas the system components and complexity increases. Further, theredundancy of execution time gets multiplied by the number of interfacesof the virtualization management system. For example, the system mayhave a Graphical User Interface (GUI), an Application ProgrammingInterface (API), a Command Line Interface (CLI), or any other interfaceor a combination thereof. The technical solutions described hereinovercome such limitations of manual testing and shorten the test cycletime, by providing a robust and automated multi-interface testing.

FIG. 3 illustrates an example virtualization management system 102. Thevirtualization management system 102 provides a single point ofmanagement across multiple types of system platforms and theirvirtualization technologies. For example, as illustrated, thevirtualization management system 102 manages a cloud-basedinfrastructure 110 of an enterprise. The cloud-based infrastructure 110is a cloud computing environment 50 as described herein. For example,The cloud-based infrastructure 110, depending on size of the enterprise,includes one or more data servers 112A-112E, one or more databaseinstances 114A-114C, one or more virtual machines 118A-118D, one or moreclusters 116A-116E, and one or more computer network nodes, among othercomponents. For example, the data servers 112A-112E may include anenterprise email server, a document server, a compute server, or anyother server that provides data and/or computation functionality tousers. The database instances 114A-114C may include an instance of acustomer database, an instance of payroll database, or any otherdatabase. The clusters 116-116E may include physical or virtual computerclusters. For example, the clusters may include a HADOOP™ cluster, a SQLSERVER™ cluster, a MICROSOFT WINDOWS SERVER™ cluster, or any othercluster. The virtual machines 118-118D include a virtual machine thatmay is tasked for a particular operation, a virtual machine that isassigned to a particular user, or any other type of virtual machines.

Users 105 of the cloud infrastructure 110, access the cloudinfrastructure 110 from within or from outside the cloud infrastructure110. For example, a user may access the resources or components withinthe cloud infrastructure 110 via the virtual machine 118A.Alternatively, a user may access the components within the cloudinfrastructure 110 via a client-device, such as one from client-devices120A-120C. The client-devices may include a communication device such asa laptop, a tablet computer, a smartphone, a mobile phone, a desktopcomputer, or any other communication device.

The cloud infrastructure 110 may communicate with another cloudinfrastructure. In an example, a user may request communication betweenthe cloud infrastructure 110 and the other cloud infrastructure, forexample to copy or move data from one place to another. The other cloudinfrastructure may include similar or different components in comparisonto the cloud infrastructure 110.

Thus, the virtual management system 120 facilitates communication withthe cloud infrastructure 110 to varying types of devices and for variouspurposes. Accordingly, to facilitate communications for the variouspurposes, the virtual management system 102 provides multiple interfacesto communicate with the cloud infrastructure 110, such as a GUI, an API,a CLI, or any other interface or a combination thereof. For example,consider a cloud infrastructure of an organization that sells goods viathe web. The data servers for the organization include information aboutgoods for sale. A user, such as a customer, may access the data via theGUI. Another user, such as an employee of the organization may accessthe data via an API, such as to change the data programmatically. Inanother example, another user, such as another server from an advertisermay access the data via the API to access and post the information on aweb site or as a search result. In addition, a network administrator mayaccess the data server via the CLI, for example to determine integrityof the server. Thus, the virtualization management system 130 providesmultiple interfaces, at least three interfaces to facilitatecommunication.

In addition, the virtualization management system 102 facilitatesmanaging the cloud infrastructure 110 from an administrativeperspective. For example, the virtualization management system 102manages images of Operating Systems (OS) that may be deployed across thecloud infrastructure 110. For example, the virtualization managementsystem 102 orchestrates emulating scaled up versions of the cloudinfrastructure 110 that supports arbitrary concurrent multi-end users.In an example, the virtualization management system 102 manages the OSimages deployed throughout the cloud infrastructure 110. Managing the OSimages includes deploying guest OS images, capturing guest OS images,importing virtual appliances (guest OS image), viewing or listing guestOS images, deleting guest OS images, and other such operations and acombination thereof. The virtualization management system 102 furtherscale and stress tests the image management repository by facilitatingrevision control, rebase (re-image), and advanced search for VirtualAppliances (VA's).

The virtualization management system 102 further manages system pools(clusters) in the cloud infrastructure 110. For example, thevirtualization management system 102 creates, lists, removes, and editsdata servers and storage system pools (storage clusters). Thevirtualization management system 102 also deploys images into serversystem pools by adding, listing, removing, and editing server hosts fromserver system pools (server clusters). In addition, the virtualizationmanagement system 102 adds, lists, removes, and edits storage subsystemhosts from storage system pools (storage clusters). The virtualizationmanagement system 102 also monitors server and storage system pools.Based on the monitoring, the virtualization management system 102creates, lists, removes, and edits workloads of the clusters. Forexample, the virtualization management system 102 set workloads to HighAvailability (HA) and have automatically places jobs in system pools.

In addition, the virtualization management system 102 may facilitateupdating firmware of the devices in the cloud infrastructure 110. Thevirtualization management system 102 may also be tasked with identifyingand integrating new devices into the cloud infrastructure 110.

Thus, the virtualization management system 102 system is responsible fora multitude of tasks, and the virtualization management system 102provides multiple interface to perform each of these tasks. Hence,system level testing of such multi-interface dynamic infrastructurewhere a complex customer change window takes place is challenging. Thetechnical solutions described herein test the multi-interface virtualmanagement system 102 using automated testing that includesstress-testing the cloud infrastructure 110 managed by virtualizationmanagement system 102.

FIG. 4 illustrates an example testing environment 200 for testing thevirtualization management system 102 and the heterogeneous cloudinfrastructure 110. The testing environment 200 includes a test server205 that communicates with both the virtualization management server 102and the cloud infrastructure 110. The test server 205 includes, amongother components, a processor 210, a memory 220, a user interface 230, atest generator 250, a multi-interface compare unit 260, and a resultcompare unit 270. In an example, the test generator 250, themulti-interface compare unit 260, and the result compare unit 270 areprogram modules that include computer executable instructions that areexecutable by the processor 210.

The processor 210 may be a central processor of the test server 205, andmay be responsible for execution of an operating system, controlinstructions, and applications installed on the test server 205. Theprocessor 210 may be one or more devices operable to execute logic. Thelogic may include computer executable instructions or computer codeembodied in the memory 220 or in other memory that when executed by theprocessor 210, cause the processor 210 to perform the featuresimplemented by the logic. The computer code may include instructionsexecutable with the processor 210. The computer code may includeembedded logic. The computer code may be written in any computerlanguage now known or later discovered, such as C++, C#, Java, Pascal,Visual Basic, Perl, HyperText Markup Language (HTML), JavaScript,assembly language, shell script, or any combination thereof. Thecomputer code may include source code and/or compiled code. Theprocessor 210 may be a general processor, central processing unit,server, application specific integrated circuit (ASIC), digital signalprocessor, field programmable gate array (FPGA), digital circuit, analogcircuit, or combinations thereof. The processor 210 may be incommunication with the memory 220 and the other components of the testserver 205.

The memory 220 may be non-transitory computer storage medium. The memory220 may be DRAM, SRAM, Flash, or any other type of memory or acombination thereof. The memory 220 may store control instructions andapplications executable by the processor 210. The memory 220 may containother data such as images, videos, documents, spreadsheets, audio files,and other data that may be associated with operation of the test server205.

The test server 205 includes a user interface 230 that facilitatesissuing commands to the test server 205. For example, a tester mayinitiate the testing by the test server 205 via the user interface 230.

FIG. 5 illustrates example logic used by the test server 205 to test thevirtualization management system 102. The test generator 250 generatestest cases that stress, scale and performance test the virtualizationmanagement system 102, as shown at block 305. For example, the testgenerator 250 is a pseudo-random test case generator. In an example, thetest generator 250 generates a random string of valid multi-interfacefunctionalities where each function can appear within the string one ormore times. The test generator 250 generates multiple such strings, eachstring being a separate test case. There are no dependencies among thegenerated functionalities in the strings and, therefore, the test casegeneration is allowed to include functionalities that could return badreturn codes. For example, a multi-interface function “RemoveHost” maybe the first command in the generated string. In this case, the machineis expected to respond a return code indicating that there are no hoststo be removed (since the first command is to remove a host withoutloading one).

The processor 210 sends the strings of multi-interface functions to boththe System Under Test (SUT), which is the virtualization managementsystem 102 that is being tested, and the result predictor 280 within theresult predictor 280. Each test case tests multiple interfaces of thevirtualization management system 102, as shown at blocks 310, 320, and330. In the illustration, the GUI, the CLI, and the API of the SUT, thatis the virtualization management system 102, are tested. The functionslisted in the string of the test cases are implemented by the SUT viaeach of the interfaces. The test server 205 receives the results for thetests cases from the SUT from each of the interfaces tested, as shown atblocks 315, 325, and 335.

The result predictor 280 identifies the expected results for thegenerated test cases. For example, the result predictor 280 simulatesthe cloud infrastructure 110 under test and further simulates executionof the test cases, as shown at block 350. In an example, the resultpredictor 280 executes each test case for each of the multipleinterfaces provided by the SUT. The simulation of each multi-interfacefunction is based on the initial values as well as previously executedfunction. For example, if a number of consecutive multi-interface‘AddHost’ functions are executed, the simulation unit keeps the list ofunique and valid hosts that exist in the pool at any given time. Thevirtualization management system 102 uses Unique Object ID (UOID) orGlobal Unique ID (GUID) for each object in the cloud infrastructure 110,such as host servers. The test server 205 uses the UOID property to keeptrack of the valid hosts that exist in the pool (cluster).

The test server 205 captures and stores results from the resultpredictor 280 in response files. In an example, results from themulti-interface SUT are appended into the response files, after theresults from the result predictor 280. Alternatively, the test sever 205maintains two separate response files, one for results from the resultpredictor 280 and one for results from the SUT. In an example, for eachpossible function per interface, the test server 205 creates two files(response files) that are updated each time the function is executed.The results from the SUT and RPS are appended to their respective files.

The multi-interface compare unit 260 compares results from all theinterfaces, as shown at block 340. The multi-interface compare unit 260compares the actual results with expected results of the test case thatwas executed. Alternatively or in addition, the multi-interface compareunit 260 compares the results from each interface to determine if theresults are identical. If the results are not identical, themulti-interface compare unit 260 determines and reports an error, asshown at blocks 345 and 347. In an example, the response filecorresponding to the SUT is appended with results from the SUT only ifthe multi-interface compare unit 260 does not encounter an error.

The result compare unit 270 compares all the accumulated multi-interfaceexpected results in the response file for the SUT to those returned bythe result predictor 280, to determine respective outcomes of the testcases, as shown at block 360. For example, at the end of the test caseexecution, the response file(s) is (are) parsed to determine presence ofkeywords (such as UOID or GUID) for both the SUT and the resultpredictor 260. For example, in case of two files, one for each of theSUT and the result predictor 280, the result compare unit 270 scans bothfiles to identify presence of a keyword. If the result compare unit 270determines an error when scanning the results for a test case, then thetest server 205 reports an error for the test case, as shown at blocks365 and 367. For example, if an expected keyword response is not presentin the file corresponding to the SUT, the file that contains actualresults, and is present in the file corresponding to the RPS (or viceversa), then the test server 205 reports an error. Alternatively or inaddition, the test server 205 reports an error if a response in the filefor the SUT is different from a corresponding response in the file forthe RPS. The test server 205 also reports an error if the results in thetwo files are the same, but do not match expected test results.

Thus, the multi-interface automated testing emulates and tests thevirtualization management system 102 by executing an arbitrary mixtureof multi-interface virtualization management functionalities in theheterogeneous cloud based infrastructure 110. For example, the teststring may test a data server of the multi-interface virtualizationmanagement system 102 through a complex hostile environment that isanchored from server, storage, and network administrator perspective.Table 1 lists a possible sequence of operations to test thevirtualization management system 102 in this manner.

TABLE 1 MIF = Multi-interface functions: A list of randomly generatedmulti-interface functions. Each function will have it's multi-interfaceversions generated such as GUI, CLI and API. ARC[i] = ARC: actual (fromthe SUT) response of the ith function ERC[i] = ARC: expected response ofthe ith function  1. Generate n number of multi-interface functions MIF:where n is a  random number and MIF is list of generated multi-interfacefunctions.  Each generated function will consists of multiple versionsof it's three  interfaces (GUI, CLI, API) supported.  2. For eachmulti-interface function mlf in MLF   a. Execute all of it'smulti-interface versions mlf on both the SUT   and RPS    i. Compare theoutputs of each function interface (GUI, CLI, API)    versions    ii. ifno error continue on with next step b. Otherwise report an    error forincompatible results between the different interfaces.   b. appendresult to a ARC[mlf] and ERC[mlf]  3. For each ARC and ERC   a. Compare(check keywords) all entries of ARC and ERC   b. if no error continue tostep 1 Otherwise report an error

FIG. 6 illustrates example logic to test the virtualization managementsystem 102. The logic may be implemented by the test server 205. Thetest server 205 determines the number of interfaces supported by thevirtualization management system 102, as shown at block 405. In anotherexample, a user may input the number of interfaces. The test server 205generates one or more test cases, as shown at block 407. The test caseincludes a sequence of instances of commands executable by thevirtualization management system 102.

The test server 205 generates a response file for each unique command inthe test case. For example, the test server 205 generates a firstresponse file corresponding to a command tested by the virtualizationmanagement system 102, and a second response file corresponding to thecommand tested by the result predictor 280, as shown at blocks 410 and430. Each instance of the commands in the test case is executed by thevirtualization management system 102 and the result predictor, via eachinterface, as shown at blocks 412 and 432. The test server 205 sends thetest case to each interface that is supported by the virtualizationmanagement system 102. The test server 205 further sends the test caseto the result predictor 280 to test each interface using the resultpredictor 280.

The test server compares the results from each interface of thevirtualization management system, as shown at block 415. If the resultsfrom each interface are not identical, the test server 205 reports anerror, as shown at blocks 418 and 417. For example, the error may bereported as an email, as a prompt on a display, an audible, or in anyother manner. Alternatively, if the results from each interface areidentical, the results from the virtualization management system 102 isappended to the first response file corresponding to the virtualizationmanagement system, as shown at block 420. If all commands in the testcase are not executed (i.e. tested), the test server 205 continues totest further instances of the commands in the test case, as shown atblock 422. The test server 205 generates and tests other tests cases tocompletely test the virtualization management system, as shown at block425.

The test server 205 compares the results from each interface of theresult predictor 280, as shown at block 435. If the results from eachinterface are not identical, the test server 205 reports an error, asshown at block 438. For example, the error may be reported as an email,as a prompt on a display, an audible, or in any other manner.Alternatively, if the results from each interface are identical, theresults from the result predictor 280 is appended to the second responsefile corresponding to the result predictor 280, as shown at block 440.If all commands in the test case are not executed (i.e. tested), thetest server 205 continues to test further instances of the commands inthe test case, as shown at block 442. The test server 205 generates andtests other tests cases to stress the virtualization management system,as shown at block 445. The test server 205 sends to the result predictor280, all the test cases that were used to test the virtualizationmanagement system 102.

The test server 205 compares the results from the virtualizationmanagement system 102 and the results from the result predictor 280, asshown at block 450. For example, the test server 205 compares theresults that are stored in the first response file and the secondresponse file. If the results in the two files are not identical, thetest server 205 reports an error, as shown at block 452. The test server205 parses the response files to compare the results based on objectidentifiers that the test server 205 assigns to each object in thevirtualization management system 102. For example, each server, eachcluster, each virtual machine, or any other component in the cloudinfrastructure 110 is assigned a unique identifier.

For example, assume that the test server 205 is testing the effect andresults of the functions of AddHost (AH), RemoveHost (RH) and ListHost(LH) across multiple interfaces of the virtualization management system102. Here, AH-x mean AddHost x and RH-y represent RemoveHost y. Considerthat a generated random command string for a test case isRH-A->RH-D->LH->AH-C->LH->RH-C->LH. The test server 205 sends thecommand string to the SUT and the result predictor 280, which executethe commands listed in that sequence. The test server 205 receives theresults after each command and appends the results to the respectiveresponse files.

Thus, the string is executed on the SUT and the result predictor 280.The multi-interface compare unit 260 compares the response from themultiple interfaces for each function for compatibility, to check ifthey all produce identical results. For example, the multi-interfacecompare unit 260 determines if the AddHost(H) versions of GUI, CLI, andAPI interfaces all report successful results. Subsequently, the responseof the SUT to each function is parsed and checked for keywords such asUOID and GUID. The response is appended to the response filecorresponding to the function for the SUT.

FIG. 7 illustrates a flowchart for testing the virtualization managementsystem 102 according to another embodiment. The logic may be implementedby the test server 205. The test server 205 determines the number ofinterfaces supported by the virtualization management system 102, asshown at block 705. In another example, a user may input the number ofinterfaces. The test server 705 generates one or more test cases, asshown at block 707. The test case includes a sequence of instances ofcommands executable by the virtualization management system 102. Thetest server 205 selects a subset of the interfaces supported by thevirtualization management system 102 that are to be tested. For example,the test server 205 tests only the GUI and the API of the virtualizationmanagement system 102, which additionally supports the CLI. Othercombinations are of course possible. In an example, a user inputs theinterfaces that are to be tested. The test server 205 executes the testcase that was generated using each of the selected interface to betested, as shown at block 712. The test server 205 executes the testcase on the SUT to ensure that each selected interface returns anidentical result, as described herein such as with respect to FIG. 6.The test server 205 generates a first response file for each command forthe SUT as described herein. In addition, the test server 205 predictsresults of the test case for each selected interface to be tested usingthe result predictor 280, as shown at block 732. Again, the test server205 ensures that the results from each selected interface are identicalusing the result predictor, as described herein such as with respect toFIG. 6. The test server 205 generates a second response file for eachcommand for the result predictor 280 as described herein. In caseadditional test cases are to be executed and/or predicted, the testserver 205 repeats the above process, as shown at blocks 725 and 745. Inan example, the user may indicate a maximum number of test cases thatare to be used to test the virtualization management system 102.Alternatively, the maximum number of tests case may be a predeterminedvalue or a randomly generated value in other examples.

Once the maximum number of test cases are completed, the test server 205compares the results for each command from the SUT and the resultpredictor, as shown at block 750. For example, the test server 205compares the results that are stored in the first response file and thesecond response file. If the results in the two files are not identical,the test server 205 reports an error, as shown at block 752. In thiscase, the first and second response files include results for each ofthe selected interfaces and not all of the interfaces that are supportedby the virtualization management system 102.

In this particular example test case, the expected results are that thefirst two functionalities in the string return invalid return codessince there are no hosts to be removed from the pool. The list hostfunction should indicate an empty set. The second LH function shouldindicate host C to be in the pool and the last LH function should showan empty list of pool since host C removed.

The result predictor 280 uses accumulated state of the pool andsimulates results for each multi-interface function. For example, theresult predictor 280 sets initializes a pool with an empty set of validhosts in the pool. Accordingly, during simulation, the first twofunctions (RH) return invalid response codes since the pool is empty inboth cases. The first LH function looks at the set of valid pool andfinds it empty. The test server 205 collects and stores the responsefrom the simulations by the result predictor 280 in a correspondingresponse file for the function.

The result comparison unit 270 parses the corresponding response filesreturned by the SUT and result predictor 280. The result comparison unit270 checks that each entry pair of the response files is consistent andindicates proper (expected) results. Accordingly, the number of entriesin each of the corresponding response files is the same for the resultsto match without an error. For example in this case, the LH responsefile in both, the SUT and the result predictor should include 9 (nine)entries (three entries*three interfaces), since the LH command wasexecuted three times and the virtualization management system 102 in theexample supports three interfaces (API, CLI, and GUI).

Thus, the technical solutions described herein facilitate testingmultiple interfaces of a virtualization management systemfunctionalities by orchestrating to emulate a scaled up cloudinfrastructure that supports arbitrary concurrent multi end users.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application, or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer-implemented method for automatedtesting of a virtualization management system, the method comprising:generating, by a test server, a test case comprising a plurality ofinstances of commands executable by the virtualization managementsystem; sending, by the test server, the test case to each interface ofa plurality of interfaces supported by the virtualization managementsystem; generating, by the test server, a response file corresponding toeach of the plurality of commands in the test case; comparing, by thetest server, results from each interface to an instance of a commandfrom the test case upon execution of the instance of the command by thevirtualization management system; in response to the results from eachinterface of the virtualization management system being identical,storing the results from the virtualization management system in theresponse file corresponding to the command; and reporting, by the testserver, an error in response to the results from each interface of thevirtualization management system not being identical.
 2. Thecomputer-implemented method of claim 1, wherein each response filecorresponding to a command comprises an entry for each instance of saidcommand executed by the virtualization management system via eachinterface.
 3. The computer-implemented method of claim 1, wherein theresponse file is a first response file for the virtualization managementsystem, the method further comprising: sending, by the test server, thetest case to a result predictor unit; simulating, by the resultpredictor unit, the command instances in the test case; generating, bythe test server, for each interface, a second response filecorresponding to each unique command in the test case, comparing, by thetest server, results from each interface to the instance of the commandfrom the test case upon execution of the instance of the command by theresult predictor; in response to the results from each interface beingidentical, storing, by the test server, in the second response filecorresponding to the command, the results from the result predictor; andreporting, by the test server, an error in response to the results fromeach interface of the result predictor not being identical.
 4. Thecomputer-implemented method of claim 3, further comprising: comparing,by the test server, the results stored in the first response file andthe second response file; and in response to the results from the firstresponse file not being identical to the results from the secondresponse file, reporting, by the test server, an error.
 5. Thecomputer-implemented method of claim 1, wherein the interfaces compriseat least two of a command line interface, a graphical user interface,and an application programming interface.
 6. The computer-implementedmethod of claim 1, wherein the instances of the commands in the testcase are executed in sequence.
 7. The computer-implemented method ofclaim 1, wherein the instances of the commands in the test case includea first instance of the command and a second instance of said command.8. The computer-implemented method of claim 7, wherein the results ofthe second instance executed via an interface are appended in theresponse file corresponding to the interface, wherein the response filecontains results of the first instance executed via said interface.